The information provided herein is generated by experimental artificial intelligence and is for informational purposes only.
supreme court hears appeal on tom hayes unsafe conviction for interest rate rigging
The UK's Supreme Court is reviewing the conviction of former UBS and Citigroup trader Tom Hayes for rigging a key interest rate, with arguments presented that the trial judge inadequately directed the jury during the summation. This three-day hearing aims to assess the fairness of Hayes' 2015 conviction and subsequent imprisonment.
former trader seeks to overturn libor rigging conviction in supreme court
Tom Hayes, the former UBS trader at the center of the Libor rigging scandal, is appealing to the UK’s Supreme Court to overturn his conviction, arguing that banks should be allowed to consider their trading advantages in rate submissions. His case could impact other convictions and challenge the Serious Fraud Office's prosecutorial strategies. Hayes, sentenced to 11 years in 2015, has maintained his innocence since his release in 2021.
ex-ubs trader seeks to overturn libor rigging conviction in supreme court
Tom Hayes, the former UBS trader at the center of the Libor rigging scandal, is appealing to the UK Supreme Court to overturn his 2015 conviction. His legal team argues that it was permissible for banks to consider their trading advantages when submitting Libor rates, claiming that the jury was misled about this aspect. A ruling in Hayes' favor could challenge multiple convictions related to rate manipulation and raise questions about the Serious Fraud Office's prosecutorial strategies.
Seems like the connection with the server has been lost. It can be due to poor or broken network. Please hang on while we're trying to reconnect...
Oh snap! Failed to reconnect with the server. This is typically caused by a longer network outage, or if the server has been taken down. You can try to reconnect, but if that does not work, you need to reload the page.
Oh man! The server rejected the attempt to reconnect. The only option now is to reload the page, but be prepared that it won't work, since this is typically caused by a failure on the server.